Skip to content

Use IConfigurationBuilder, IConfiguration, and Typed Configuration to centralize the way we manage CLI behaviors #49761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

baronfel
Copy link
Member

This is a draft that's building on the work that the test team started with dotnet.config - if we can get the majority of the CLI working on a shared IConfiguration-based configuration layer/abstraction, then we can separately evolve the things that feed in to that configuration.

This is a mostly-vibe-coded draft of that idea - now I want to see what CI thinks.

@baronfel baronfel force-pushed the unified-iconfiguration branch from 14bd2b6 to 595351e Compare July 16, 2025 02:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CLI config-system-candidate Issues that could be solved cleanly if the .NET CLI had a git-like configuration system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant